home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d22
/
wssi338b.arc
/
WSSM330.DOC
< prev
next >
Wrap
Text File
|
1988-09-16
|
3KB
|
67 lines
Copyright (C) 1988 by Robert W. Babcock and WSS Division of DDC
All Rights Reserved
Instructions for WSSMERGE version 3.30
WSSMERGE.EXE merges two WSSINDEX databases. Only databases
written by WSSINDEX version 2.0 or higher can be merged. Older
databases can be converted by loading them into a current version
of WSSINDEX and resaving them.
To use the program, just answer the prompts for the names of the
input, output and merged databases (complete names, there are no
default values). Drive and subdirectory qualifiers are allowed.
The disk space required for the output file will be approximately
the sum of the input sizes, but the entire merged database will
not be in core at once, so you may be able to create a database
larger than you can restore. In fact, you can exceed the 16K
file limit, but you will not be able to read such a file with
WSSINDEX on any machine.
When merging, you can elect to assign a common category to all
files from the first database, and a second category to files
from the second database. This might be useful if you had small
databases organized by category, and wanted to merge them into a
single database. You can suppress either common category by just
hitting return when prompted for the category. In any case,
previously entered categories are not changed.
One error which the program may warn you about after completing
the merging operation is duplicate volume names in the database.
The duplicate entries are not deleted from the merged database;
that task is left to you. Probably you should decide which input
database has the most recent information (perhaps by checking the
date indexed), and remove the matching entry from the other
database, then remerge. Or if you have assigned the same name to
two disks, use the Label and Rename options in WSSINDEX.
[Version 1.00 of WSSMERGE, which was sent to only one person, did
not check for duplicate volume names. Version 1.10 of WSSMERGE
cannot properly merge databases produced by WSSINDEX version 3.xx
if .ARC file info has been extracted, nor will it recognize that
there is a problem.]
In a future release, I hope to add proper handling of duplicate
volume names, probably giving the user the option of selecting
which copy to accept. (This is harder to implement that might be
expected, and no one has complained about this omission.)
Robert W. Babcock
WSS Division of DDC
4 Reeves Road
Bedford, MA 01730
USA
617-275-1183